Skip to content
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.

Work after switching to attrs #45

Closed
4 of 9 tasks
astrojuanlu opened this issue Nov 6, 2019 · 5 comments
Closed
4 of 9 tasks

Work after switching to attrs #45

astrojuanlu opened this issue Nov 6, 2019 · 5 comments

Comments

@astrojuanlu
Copy link
Member

astrojuanlu commented Nov 6, 2019

(Copied from #44)

This already passes all the tests locally.

Things that will have to be reworked:

  • Shortcuts, converters

Things I removed and I'd like to bring back:

  • Docstrings

Things I'd like to review:

  • Defaults (we should probably be using default=None everywhere)
  • isinstance (we are inconsistently using positive and negative checks)
  • Validation (we use __attrs_post_init__ but we could use @x.validator instead http://www.attrs.org/en/stable/init.html#decorator)
  • Mixins (are they necessary?)
  • KNOWN_PROPERTIES (can I iterate over attrs properties now instead?)
  • Enumerations (including missing StripeOrientationValue)

Things I'd like to add in the future:

@noc0lour
Copy link

noc0lour commented Dec 4, 2019

Note: The example in README is not working since CZMLWidget now expectes a Document() to be passed instead of a list. Now either a Document(simple) has to be passed or CZMLWidget has to do it in the initalizer.

Edit: For simple it works because it's a Document now, but it doesn't work for a list of packets. I don't know what would be the right way here. Maybe just a documentation issue.

@astrojuanlu
Copy link
Member Author

@noc0lour I'd say that CZMLWidget should always expect a Document, do you see any inconsistency in the README or any docstring?

@noc0lour
Copy link

noc0lour commented Dec 4, 2019

No, somehow I expected in poliastro to be able to stick results from the CZML_extractor directly into a CZMLWidget, which is a poliastro issue not a czml3 issue.

@astrojuanlu
Copy link
Member Author

Oh, I see! Yep, CZMLExtractor should produce a Document with a proper Preamble.

@Stoops-ML
Copy link
Collaborator

Closing as not relevant as of #154

@astrojuanlu astrojuanlu closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants