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

use OrderedDict in byteify #561

Merged
merged 3 commits into from
Feb 1, 2019
Merged

use OrderedDict in byteify #561

merged 3 commits into from
Feb 1, 2019

Conversation

alexcjohnson
Copy link
Collaborator

Quick followup to #545 - We maintain order in py3, but in py2 where we run the objects through byteify they were reverting to regular dict. This keeps them as OrderedDict.

Tested against dcc locally.

@@ -25,8 +25,8 @@
)

component$props <- filter_null(component$props)

structure(component, class = c('dash_component', 'list'))
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this trailing whitespace wasn't caught by CI earlier... it's going to generate diffs in all the component packages that use it.

Copy link
Contributor

@T4rk1n T4rk1n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💃

@alexcjohnson alexcjohnson merged commit 0f27d78 into master Feb 1, 2019
@alexcjohnson alexcjohnson deleted the ordered-byteify branch February 1, 2019 02:15
HammadTheOne pushed a commit to HammadTheOne/dash that referenced this pull request May 28, 2021
Fix Min/Max DatePickerRange date
AnnMarieW pushed a commit to AnnMarieW/dash that referenced this pull request Jan 6, 2022
Fix Min/Max DatePickerRange date
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants