Skip to content

Rename Instance private options and __options#4429

Merged
janmeier merged 1 commit intosequelize:masterfrom
andywhite37:master
Sep 9, 2015
Merged

Rename Instance private options and __options#4429
janmeier merged 1 commit intosequelize:masterfrom
andywhite37:master

Conversation

@andywhite37
Copy link
Copy Markdown
Contributor

- Possibly fix sequelize#4423
- Rename Instance `options` to `$options` to prevent value
  overwriting with models that have a column named `options`
- Also rename Instance `__options` to `$modelOptions` to avoid confusion
  between $options and __options.
@janmeier
Copy link
Copy Markdown
Member

janmeier commented Sep 9, 2015

Looks good to me - good catch on the __options - model options is definitely a better name

This shouldn't require a major version right @mickhansen ? Do you agree that if people depend on .options its their own fault ;) ?

@mickhansen
Copy link
Copy Markdown
Contributor

It's not documented anywhere, so can hardly be considered public API. I personally probably have some code dependant on that somewhere, but yeah i'd agree that if people are using non-public stuff they can't expect SEMVER to apply there.

@janmeier
Copy link
Copy Markdown
Member

janmeier commented Sep 9, 2015

Cool, I'll merge and add it to the changelog then

janmeier added a commit that referenced this pull request Sep 9, 2015
Rename Instance private options and __options
@janmeier janmeier merged commit 3c0d233 into sequelize:master Sep 9, 2015
janmeier added a commit to janmeier/sequelize that referenced this pull request Sep 9, 2015
janmeier added a commit that referenced this pull request Sep 9, 2015
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

Successfully merging this pull request may close these issues.

Query with include returns an array with one object containing all null values (because there is a column named options in the model)

3 participants