Skip to content
Permalink
Branch: master
Commits on Sep 9, 2019
  1. Merge pull request #60 from 4teamwork/jone-plone5-fix-tests

    jone committed Sep 9, 2019
    Fix tests for Plone 5.
  2. Fix tests for Plone 5.

    jone committed Sep 9, 2019
    The test was relying on the fact that getDependenciesForProfile did
    not check whether the profiles actually exist.
    But this was changed from Plone 4 to 5, getDependenciesForProfile now
    verifies that the profiles actually exist.
    
    The test is rewritten to use actually generated profiles, so that the
    verification passes.
Commits on Jun 20, 2017
  1. Back to development: 1.11.2

    mbaechtold committed Jun 20, 2017
  2. Preparing release 1.11.1

    mbaechtold committed Jun 20, 2017
  3. Merge pull request #56 from 4teamwork/mba/nitpicking

    jone committed Jun 20, 2017
    Nitpicking
  4. Fix typos.

    mbaechtold committed Jun 20, 2017
  5. Remove unused import.

    mbaechtold committed Jun 20, 2017
Commits on Jun 16, 2017
  1. Back to development: 1.11.1

    jone committed Jun 16, 2017
  2. Preparing release 1.11.0

    jone committed Jun 16, 2017
  3. Merge pull request #55 from 4teamwork/jone-global-ticking-creator

    jone committed Jun 16, 2017
    Make it possible to install a ticking creator globally.
Commits on Jun 15, 2017
  1. Make it possible to install a ticking creator globally.

    jone committed Jun 15, 2017
    In order to let nested creators tick the clock too, the ticking creator
    can be installed globally when used as context manager.
    
    In order to support replacing the creator a chain is used internally,
    allowing to register any amount of creator wrappers without the need to
    monkey patch the create function.
Commits on May 8, 2017
  1. Merge pull request #54 from 4teamwork/pv-fix_for_plone_5.1

    jone committed May 8, 2017
    fix for plone 5.1
Commits on May 2, 2017
  1. Changelog update

    Pablo Vergés
    Pablo Vergés committed May 2, 2017
  2. Dexterity image builder requires a `NamedImage`

    Pablo Vergés
    Pablo Vergés committed May 2, 2017
  3. Asks catalog instead of index (query lazyness)

    Pablo Vergés
    Pablo Vergés committed May 2, 2017
    With the actual version of Plone, tasks are queued for query lazyness.
    Querying the index does not process the task queue, preventing the created
    object from providing the required interface.
    Querying the catalog polls the task queue.
    
    Ref: Products.CMFCore.CatalogTool.searchResults
  4. Adds `session` import to usage section in README

    Pablo Vergés
    Pablo Vergés committed May 2, 2017
  5. Using plone 5.1 instead of 4.3

    Pablo Vergés
    Pablo Vergés committed May 2, 2017
Commits on Apr 4, 2017
  1. Merge pull request #53 from 4teamwork/mle-plone51

    jone committed Apr 4, 2017
    Test against Plone 5.1.x instead of Plone 5.0.x.
  2. Test against Plone 5.1.x instead of Plone 5.0.x.

    maethu committed Apr 4, 2017
Commits on Mar 1, 2017
  1. Back to development: 1.10.1

    jone committed Mar 1, 2017
  2. Preparing release 1.10.0

    jone committed Mar 1, 2017
  3. Merge pull request #52 from 4teamwork/jone-ticking-create

    jone committed Mar 1, 2017
    Add "ticking_creator", ticking a freezed clock.
  4. Add "ticking_creator", ticking a freezed clock.

    jone committed Feb 28, 2017
    With ``ftw.testing`` it is possible to
    `freeze the time <https://github.com/4teamwork/ftw.testing#freezing-datetime-now>`_.
    
    When freezing the time and creating multiple objects, they will all end up with
    the same creation date. This can cause an inconsistent sorting order.
    
    In order to solve this problem, ``ftw.builder`` provides a ``ticking_creator``,
    which moves the clock forward after each time an object is created.
    This means we have distinct, consistent creation dates.
    
    Usage example:
    
        from datetime import datetime
        from ftw.builder import Builder
        from ftw.builder import ticking_creator
        from ftw.testing import freeze
    
        with freeze(datetime(2010, 1, 1)) as clock:
            create = ticking_creator(clock, days=1)
            self.assertEquals(DateTime(2010, 1, 1),
                              create(Builder('folder')).created())
            self.assertEquals(DateTime(2010, 1, 2),
                              create(Builder('folder')).created())
            self.assertEquals(DateTime(2010, 1, 3),
                              create(Builder('folder')).created())
Commits on Sep 19, 2016
  1. Back to development: 1.9.1

    jone committed Sep 19, 2016
  2. Preparing release 1.9.0

    jone committed Sep 19, 2016
  3. Merge pull request #51 from 4teamwork/jone-properties

    mbaechtold committed Sep 19, 2016
    add ".with_property" method to content builders.
  4. add ".with_property" method to content builders.

    jone committed Sep 19, 2016
    Extend content builders with a ``.with_property`` method.
    
    The internal ``set_properties`` method call is in the AT and DX specific
    implementations in order to make sure that it happens before the object
    is indexed, as the indexers may depend on a correctly set property.
Commits on Jun 30, 2016
  1. Back to development: 1.8.2

    jone committed Jun 30, 2016
  2. Preparing release 1.8.1

    jone committed Jun 30, 2016
Commits on Jun 29, 2016
  1. Back to development: 1.8.1

    jone committed Jun 29, 2016
  2. Preparing release 1.8.0

    jone committed Jun 29, 2016
  3. Merge pull request #50 from 4teamwork/jone-contenttype-framework-switch

    maethu committed Jun 29, 2016
    Support switching builder implementation to dexterity
  4. Add content manager for switching to AT / DX content builders.

    jone committed Jun 29, 2016
Older
You can’t perform that action at this time.