Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shortname needs a better name #4

Closed
pjf opened this issue Sep 23, 2014 · 1 comment
Closed

Shortname needs a better name #4

pjf opened this issue Sep 23, 2014 · 1 comment

Comments

@pjf
Copy link
Member

pjf commented Sep 23, 2014

The shortname field in the spec is one of the most important. It's:

  • The name that ModuleManager would use when detecting the mod.
  • The name which other CKAN files use to reference the mod.
  • The name that the packaged .ckan file should be called.
  • Absolutely required for a CKAN file to be considered valid.

In other words, it's the primary identifier for the mod in question. shortname makes it sound like it's what you use when you're too lazy to type, but it's much more important than that.

I suspect identifier is probably a good choice for the field name.

pjf added a commit that referenced this issue Sep 23, 2014
pjf added a commit that referenced this issue Sep 23, 2014
pjf added a commit that referenced this issue Sep 23, 2014
@pjf
Copy link
Member Author

pjf commented Sep 23, 2014

Done. It's now identifier.

@pjf pjf closed this as completed Sep 23, 2014
politas pushed a commit that referenced this issue Apr 17, 2018
politas pushed a commit that referenced this issue Mar 15, 2019
…mn (#4)

* Save/load column names instead of list of bools

* Remove auto-managed columns from default config list

* Save/load hidden columns instead of visible

* Rename col vis config func

By @HebaruSan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant