Skip to content

personalized vs project config #86

@janiswehen

Description

@janiswehen

Problem to solve

As Squeak Developer working in a Team, I want the saved source to be poppyPrinted with a Project specific config, but still want to see the source in my browser poppyPrinted with my personalized config so that all teammembers with different personalized configs have still the same source code and no unnessecary changes that make it in the commits.

Further details

The personalized config can for now be the default Config returned by a class Method PPFormatterConfig personalizedConfig. This Method can be specialized in an other Issue further down the line.
The project specific config should be specified in a Method in the Project. There are many options for this implementation. One possibility could be a Method with a Pragma <ppProjectConfig> that can be found via the Pragma. One example could be

ppProjectConfig
	<ppProjectConfig>

	^ PPFormatterConfig default
		spacesBeforePointInArray: true;
		formatToMaxLineWidth: true;
		maxLineWidth: 120

If no Method with this Pragma is found in the Project then the project specific config is PPFormatterConfig default.

Acceptance Criteria

  • Given the project specific config. When I have prettyprint selected in the browser and press save then it gets saved poppyPrinted with the project specific config even if its displayed different.
  • Given a personalized Config. When I have prettyprint selected in the browser and press save then I want the displayed method to be poppyPrinted with the personalized Config.
  • When I have source selected in the browser and press save then the displayed Method and the saved Method is not poppyPrinted at all

Metadata

Metadata

Labels

story 📚User stories are short, simple descriptions of a feature.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions